home *** CD-ROM | disk | FTP | other *** search
- Path: news.iapc.net!hostmaster@iapc.net
- From: dyn88olds@iapc.net ("Dynamic 88 Olds, Where The Action Is In 1964")
- Newsgroups: alt.winsock.trumpet,alt.winsock,comp.dcom.modems
- Subject: Re: Comm Overrun Errors - A Possible Solution
- Date: Sun, 03 Mar 1996 07:56:11 GMT
- Organization: Internet Access Point Corporation
- Message-ID: <31394fb3.5124008@news.iapc.net>
- References: <4emn1a$5ba@trojan.neta.com> <4esm85$qd2@fountain.mindlink.net> <4f03sk$o7g@zoom2.telepath.com> <31169d53.12139962@news.gnn.com> <3122446E.5898@dircon.co.uk> <3122928A.4E3A@cerberus-sys.com> <troy-0103961527260001@denim.csn.net> <3137B792.3B0A@cerberus-sys.com>
- NNTP-Posting-Host: hou-d01-173.iapc.net
- X-Newsreader: Forte Agent .99c/16.141
-
- Put this message in the 386Enh section of your System.ini:
-
- Com(?)FIFO=1
-
- In all the MS literature the figure is misprinted as Com(whatever your
- modem is on}=on
-
- Check it out. This should help alot.
-
- howard Rubin
-